Requirements and Content Editor Change Log

17.2.0.xxxx05/02/2017 - 05/16/2017

KeepTogether and KeepWithNext not working with Tables.
  • Type: Defect
  • Reference: 452869
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue/Summary: When a table would cross between two pages it would cause half the table to stay on one side and the other half on the other, there is an option KeepTogether or KeepWithNext that should keep items on one page.
Solution: There were updates to the code to ensure that the items with the option 'KeepTogether' or 'KeepWithNext' would force those items to be on one page.
Implementation Notes: This feature requires a Requirements Editor and style sheet update.
Error opening Static REQs
  • Type: Defect
  • Reference: 459714
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue/Summary: Users get error "Object Reference not set to an instance of an object" when try to open inheritated static documents in RE3.
Solution/Technical Notes: There was a fix in the code to correct the program behavior.
Implementation Notes: This feature requires a Requirements Editor 3 update.
Copy/Paste issue on inherited
  • Type: Defect
  • Reference: 364446
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue/Summary: When user copy/paste a section into customer REQ from base, the newly pasted section is given a new section ID number. This new section is left as an inherited section and the Section ID number is not given the _ORG_BANK suffix. This causes issues in merge sections where the new base section have the same Section ID that the custom section has. Two sections having the same ID causes the merge to fail.
Solution/Technical Notes: There was a fix in the code to correct the program behavior.
Implementation Notes: This feature requires a Requirements Editor 3 update.
ChangeBlock(conflict\remaining) counts do not update on Save
  • Type: Defect
  • Reference: 453934
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue/Summary: During 3-way merge, users go through the documents and mark conflicts as resolved. As users mark conflicts and save, the conflict counts on the tab do not change to reflect the actual remaining conflcts.
Solution/Technical Notes: There was a fix in the code to correct the program behavior.
Implementation Notes: This feature requires a Requirements Editor 3 update.
Tool Bar Enabled/Disable Webservices
  • Type: Enhancement
  • Reference: 442069
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Yes documentation impact
Summary: There is a new button on the Toolbar that will allow the user to disable the URL connection from the Authoring Web Service. When you are not connected it will give the option to connect 'Enable Authoring web service' then when its enabled it will say 'Disable Authoring web services (Up now)'.
Technical Notes: This button allows for diabling the Authoring Web Service. To add this item to the tool bar you: View -> Toolbars -> Enable/Disable AUthoring WebServices.
Implementation Notes: This feature requires a Requirements Editor update.
New Stylesheet Required for URLA Dynamic Authoring
  • Type: Enhancement
  • Reference: 445593
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: Added a new stylesheet to take what was in WKFS_StyleGuide_IntegratedDisclosures style sheet and use the default tagline from WKFS_StyleGuide.
Technical Notes: New stylesheet is called WKFS_StyleGuide_URLA.
Implementation Notes: This feature requires a Content Style Sheets update.
Added Option to Print on Color Paper
  • Type: Enhancement
  • Reference: 445588
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: There is now an option for Dynamic documents that will allow them to indicate the document needs to be printed on a color paper.
Solution/Technical Notes: You add this option under InstanceDocumentRef -> Document, right click and Add Attribute -> ColoredPaper. Then you will be able to select Yes or No. To be used in the future with Expere.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.
Color Paper Option Added to XML
  • Type: Enhancement
  • Reference: 445592
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: For the build we have added the the color paper option to the XML.
Technical Notes: You can find this option in the XML by searching (ColoredPaper="). To be used in the future with Expere.
Implementation Notes: This feature requires a Requirements and Content Editor Tool and Expere Engine update.
Dynamic Tag Highlighting
  • Type: Defect
  • Reference: 397882
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: In the latest builds, was no longer showing XrefTarget, DefinedTerm, DocumentRference, Suprescript, and Hyperlink were not highlighted outside edit mode.
Solution: There was a code change to bring this functionality back.
Implementation Notes: This feature requires a Requirements Editor update.
HTML Option Removed from Options Menu
Issue: This was on oversight from another PBI and wasn't removed.
Technical Notes: Removed the HTML option in the Option screen.
Implementation Notes: This feature requires a Requirements Editor update.
Adding printing options Duplex or Simplex
  • Type: Enhancement
  • Reference: 443666
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: We will be adding the option to allow for duplex printing. This option is located in Properties (File -> Properties), there will be a drop down under Collate. You will have Simplex or Duplex option.
Technical Notes: In this problem we are only adding the option to choose the type of printing you want the document done, the xml adding will be in reference 445371.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.
Builder generating proper XML for duplex/simplex printing.
  • Type: Enhancement
  • Reference: 445371
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: In the XML for the generated document we are adding the type of printing that needs to be done for the specific document.
Technical Notes: In a Static XML you will find this new option under the ‘Template’ Node. I the Dynamic XML you will find the option under ‘Document’ Node.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.
Requirements Editor 3: Adding printing options Duplex or Simplex
Summary: You now get to choose the type of print, Simplex, Duplex, or Blank (Default printing option). The options is called 'Collate'
Technical Notes:In this problem we are only adding the option to choose the type of printing you want the document done, the xml adding will be in reference 445371.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.
Requirements Editor 3: Builder generating proper XML for duplex/simplex printing.
  • Type: Enhancement
  • Reference: 445371
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The builder now addes the new options for duplex/simplex printing to the XML.
Solution/Technical Notes: In a Static and Dynamic documents the Collate option can be found by searching (Collate="). To be used in the future with Expere.
Implementation Notes: This feature requires a Requirements and Content Editor Tool and Expere Engine update.
Update ENUMs table when adding an XPath Enumeration Data Point.
  • Type: Defect
  • Reference: 443099
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issuey: When adding an XPath Enumeration data point with enumeration data the Enums table is not updated.
Solution: Code has been modified to correctly update the table when adding the XPath Enumeration data.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.
Converting references to local references properly.
  • Type: Defect
  • Reference: 443925
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: Current when a user right clicks on reference, you have the option to click “Convert to Local Content”, when you go to the data grid it stays as a content reference.
Solution: We did updates to the code that when “Convert to Local Content” it updates the data grid properly indicated its local content.
Implementation Notes: This feature requires a Requirements and Content Editor Tool update.

Defects

Revision 2016.3.1 11/18/2016 - 06/27/2017

Note:

Requirements and Contents Editor version 2016.3 requires version 2016.3 of the Authoring Web Service.

The new Web Service is backward compatible with older versions of the Requirements and Contents Editor.

To upgrade your Web Service, replace the WebService folder (preserving your Web.config file) on the Authoring Web Server with the WebService folder placed by the 2016.3.1 Expere Server Tools installer. The location of the WebService folder is typically: 
C:\Program Files (x86)\Wolters Kluwer\Expere Server Tools\WebService

Enhancements

Testing Ancillary Output Options
  • Type: Enhancement
  • Reference: 327488
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: This enhancement provides the ability to test Ancillary Output options within the Requirements and Content Editor. Included in the Ancillary Output options are the ability to test ancillary barcodes and watermarks.

The previous method of using the config file to get AncillaryOutputs has been removed.
Implementation Notes: Under the Assembly -> Execute Document, we added another option at the bottom of the popup. You can browse to the location of the XML to test the Acnillary Output, once you have the location select you use the drop down to select the file you want to use.
Ancillary Output XML Fragment Edit Screen
Summary: This enhancement provides the ability to test ancillary barcodes within the Requirements and Content Editor. This provides users the ability to confirm the design of a document or REQ file paginates well when ancillary barcodes are incorporated.
Implementation Notes: This feature requires a Requirements and Content Editor Tool / Expere Engine / Content Style Sheets / Expere Server Tools (choose one: Expere Administration Tool/Customer Facing Outlines/Build Doc Previews/Data Dictionary Builder) update.

Defects

Revision 2016.3 08/05/2016 - 11/17/2016.

Enhancements

ExpereResponseName Attribute Added to PARA Element
  • Type: Enhancement
  • Reference: 395704
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The optional ExpereResponseName attribute has been added to the para element.
Technical Notes: This enhancement allows the user to indicate that a regular Para value should be returned in the Expere Engine response.
Implementation Notes: This feature requires a Requirements and Content Editor update.
New Option to Remove Tagline Print Date
Summary: This enhancement provides the option of removing the Tagline Print Date from a transaction.
Technical Notes: In order to employ this option, you must place the SuppressTaglinePrintDateInd element into the desired transaction as in the following example. 
<SuppressTaglinePrintDateInd>1</SuppressTaglinePrintDateInd>
The element can be placed anywhere within the root TXN element.
Implementation Notes: This feature requires a Requirements and Content Editor update.
New Interface for Registry Entries
Summary: This enhancement allows for adding, removing and editing Transaction schema fields within a user interface.
Technical Notes: A new subsection, Transaction Schemas, has been added to the Expere Options section of the Options dialog. This new subsection allows you to add, remove and edit eight different fields of the transaction schemas. for more information, refer to the Requirements and Content Editor User Guide.
Implementation Notes: This feature requires a Requirements and Content Editor update.
Local schema and interface added
Summary: This enhancement provides for the local storage of schemas. Now schemas are updated only when they are modified or the user chooses to refresh them.
Technical Notes:
  • A new menu item, Refresh Schema Files..., has been added to the Tools menu of the Requirements and Content Editor toolbar.
  • Package Schemas are saved to Program Files (x86)\Wolters Kluwer\Requirements Editor 3\Extensions\ReqEditor\Resources\Schemas, extract to C:\Users\user.name\AppData\Local\Wolters Kluwer\RequirementsEditor\3.0\Schemas
Implementation Notes: This feature requires a Requirements and Content Editor update.
Support for eSignatures in new SDX element
Summary: A new element, SignerEmail, has been added under the Signature field of both static and dynamic documents. This provides an email address that is used as part of the eSignature field for the SDX fillable field naming convention.
Technical Notes: SignerEmail can be a value or may contain a DTA. For dynamic documents, the SignerEmail element can be added as a child of Signature using standard methods. SignerEmail can be added to a static document using the Requirements and Content Editor.
Implementation Notes: This feature requires a Requirements and Content Editor update.
Schemas are now stored locally
Summary: Previously, schemas were stored on the network requiring the Requirements and Content Tool to pull the schema from the network each time a document was loaded.

Now, schemas are stored locally, reducing the schema load time when documents are opened.
Technical Notes:
  • The Config file is updated with the removal of the "<transactionSchemaSection>" attributes.
  • The Registry is updated with the new "<transactionSchema>" attributes.
Implementation Notes: This feature requires a Requirements and Content Tool Editor update.
Custom Font Support for Dynamic Documents
  • Type: Enhancement
  • Reference: 400524
  • Compliance Impacts: This item is a compliance or regulatory issue.
  • Documentation Impacts: Requirements and Content Editor
Summary: This enhancement allows users to override the default font for para and dta elements.
Technical Notes: The user can select any font listed in the Font.XML file (C:\Program Files (x86)\Wolters Kluwer\Requirements Editor 3\Extensions\ReqEditor\ExpereNet\Font.xml).
Implementation Notes: This feature requires a Requirements and Content Editor update.
Discrete Party ID Element for Static Documents
  • Type: Enhancement
  • Reference: 405346
  • Compliance Impacts: This item is a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: A new DiscretePartyID has been created for Static documents in the instance.xsd.
Technical Notes: This enhancement allows integration partners to use Expere's RembrandtID to help identify borrowers in order to manage their document packages to produce distinct/discrete borrower doc packages for delivery using a distinct document packaging solution.
Implementation Notes: This feature requires a Requirements and Content Editor update.
Discrete Party ID Element for Dynamic Documents
  • Type: Enhancement
  • Reference: 405344
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: A new DiscretePartyID has been created in the instance.xsd
Technical Notes: This enhancement allows integration partners to use Expere's RembrandtID to help identify borrowers in order to manage their document packages to produce distinct/discrete borrower doc packages for delivery using a distinct document packaging solution.
Implementation Notes: This feature requires a Requirements and Content Editor update.
Support for Custom Stylesheets in Requirements and Content Editor
  • Type: Enhancement
  • Reference: 398645
  • Compliance Impacts: This item is a compliance or regulatory issue.
  • Documentation Impacts: Requirements Editor User Guide
Summary: Requirements and Content Editor now supports the use of custom stylesheets.
Technical Notes: Note the following:
  • The content folder is only updated during document assembly.
  • Core and Repository folders are not updated each time a REQ file is opened.
  • If the install folder is empty or the Auth Web Service URL is unreachable the core folder is updated from the install folder.
  • If the core folder exists, then it is never updated from the install folder. If the core folder does not exist, it is created from the install folder.
  • The Webeservice folder is updated only if a user selects Tools > Refresh Authoring Files or if the Authoring Web Service URL changes.
  • All stylesheets in the Authoring Web Service for each precedence level are downloaded to the core folder structure.
Implementation Notes: This feature requires a Requirements Editor update.

Defects

Incorrect BRCD Value Returned
  • Type: Defect
  • Reference: 415289
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified in which an incorrect BRCD value was being returned as defined in the Custom Data column on the Package Rules tab.
Solution: Now, when PKGD files are generated, a new PackageNames attribute with the value corresponding to the Packages column on the Package Rules tab is added.
Note:
  • This applies to both static and dynamic documents.
  • Mulitple package rows included in the same rule are comma separated: i.e.,
    PackageNames="PKG.CommercialClosing,PKG.SBACommercialClosing"
Implementation Notes: This feature requires a Requirements and Content Editor update.
Inherited Documents: ORG list stalls during loading
  • Type: Defect
  • Reference:405075
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified in which the Organization Selection window would hang while creating a new inherited document.
Solution: Code has been modified to successfully create, open and assemble a new inherited document.
Implementation Notes: This feature requires a Requirements and Content Editor update.
Update Style Sheets Error Resolved
  • Type: Defect
  • Reference: 395259
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: Requirements Editor User Guide
Issue: An issue was identified in which an access error was produced while trying to update style sheets in the default location within Program Files (x86).
Solution: The following changes have been made within Requirements Editor to provide a solution.
  • The Update Stylesheets menu command has been replaced with Refresh from Authoring WebService. While this is a manual command provided to force a style sheet refresh.
  • Style sheets are now stored in C:\Users\<USERNAME>\AppData\Local\Wolters Kluwer\RequirementsEditor\3.0\core
  • Users that perform a manual copy of style sheets to <install folder>\Resources\ContentItems will now need to place them in C:\Users\<CURRENT USER>\AppData\Local\Wolters Kluwer\RequirementsEditor\3.0\Core\<ORG PRECEDENCE>.
  • When manually copying existing customized stylsheets to the Install folder, PDFs are generated using those style sheets during assembly.
Implementation Notes: This feature requires a Requirements Editor update.
Create Transaction From Document Rules Menu Item Disabled
  • Type: Defect
  • Reference: 397913
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified after a schema loads in which the Create Transaction from Document Rules... menu option was disabled (grayed) until the user first interacted with another application feature.
Solution: Code has been modified to allow for enabling the Create Transaction from Document Rules... menu option immediately after a schema has been loaded.
Implementation Notes: This feature requires a Requirements Editor update.

Revision 2016.2 04/16/2016 - 08/04/2016

  • The 2016.2.0 release of the Requirements Editor Tool has been upgraded to Visual Studio 2015. You MUST uninstall the Requirements Editor program before installing the 2016.2.0 version.
  • This upgrade also requires the Microsoft Visual C++ 2015 Redistributable component. The installation process will provide messaging to install this component if it does not exist. The C++ Redistributable executable (VC_redist.x86.exe) is located in the same folder as the install executable. Double-click on the .exe to begin the installation process; once complete, proceed with the Requirements Editor Tool installation.

Enhancements

New MilitaryLendingAct Profile
  • Type: Enhancement
  • Reference: 391987
  • Compliance Impacts: This item is a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: In order to comply with the Military Lending Act changes, a new profile has been created: MilitaryLendingAct
Technical Notes: Profiles.xml has been updated to include MilitaryLendingAct as an option under the OCP profile.
Implementation Notes: This feature requires a Requirements Editor update.
Special Output Formats for Two and Three Decimal Places
  • Type: Enhancement
  • Reference: 373969
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation Impacts: Requirements Editor User Guide
Summary: Two new output formats have been created to allow for percentages to print to two decimals or three decimals.
Technical Notes: Users can:
  • choose a special output format for either 1) two or three decimal places to print or 2) a whole number, depending on what is passed.
  • use a special output format in a PTR as a PRINTFORMAT.

This can be viewed in DocViewer.

Note the following:
  • {12 or 12.34%}: Truncate at 2 decimals; print trailing zero(s). A whole number only prints as a whole number; no trailing zero(s).
  • {12 or 12.345%}: Round to 3 decimals; print trailing zero(s). A whole number only prints as a whole number; no trailing zero(s).

Refer to the Requirements Editor User Guide for further details.
Implementation Notes: This enhancement requires a Requirements Editor update.
Option for HTML Creation of Outlines
  • Type: Enhancement
  • Reference: 377896
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation Impacts: Requrements Editor User Guide
Summary: A new option has been implemented allowing you to render outlines as HTML instead of PDF.
Technical Notes: A new option, Render as HTML, has been placed in the Options dialog. Changing this setting to True renders outlines as HTML. Default is False.
Implementation Notes: This enhancement requires a Requirements Editor update.

Defects

Update Stylesheets Function Error
  • Type: Defect
  • Reference: 394881
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An issue was identified in which updating a stylesheet (Update > Stylesheets) resulted in denied access to the selected file due to incorrectly resolving the folder pathing name.
Solution: Code was modified within Requirements Editor to allow access to the stylesheets.
Implementation Notes: This feature requires a Requirements Editor update.
Renditions Time Out Error
  • Type: Defect
  • Reference: 381111
  • Compliance Impacts: This item is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Issue: An error was identified which occurred when creating Renditions for the OCP-HE Master.req file.
Solution: Code was moified so that users can create renditions without a time out error for the OCP-HE Master.req, or any EPM req with or without content references.
Implementation Notes: This feature requires a Requirements Editor update.
Exception error when clicking the Preview Tab
  • Type: Defect
  • Reference: 377435
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified, with TRID documents only, where an exception error was displayed upon clicking the Preview Tab.
Solution: Now, when clicking the Preview Tab, the expected preview is generated and displayed.
Implementation Notes: This feature requires a Requirements Editor update.
Static Base REQs-Setting "override=true" on Template Element incorrectly
  • Type: Defect
  • Reference: 378896/373796
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: When creating a new BASE or CUSTOM static REQ (not inherited), Requirements Editor is setting the override attribute to "true" on the <Template> element. The override attribute should not be present on this element. Also, due to the presence of this attribute set to “true” incorrectly, upon importing an xTemplate for a static REQ, an error would occur stating “An error occurred retrieving the inherited compoonents: Incomplete reponse from the server...”.
Solution: Now, when creating new base/custom static REQs, there is no override attribute for the Template element.
Implementation Notes: This fix requires a Requirements Editor update.

The effective date for all products within the scope of this document for release 2016.1.2 is 06/21/2016.

Requirements Editor 3 – Updated Expere Engine for Cash to Close calculated values provided
  • Type: Enhancement
  • Reference: PBI 390383 (Engine PBIs 385920 / 387587)
  • Compliance Impacts: This item is a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact
Summary: The Requirements Editor 3 Tool has been updated to incorporate an updated version of the Expere Engine (build 3604). The engine was updated to support calculated values for Cash To Close. See PBIs 385920/387587 for further details. There are no additional requirements editor changes included this in release.
Implementation Notes: This feature requires a Requirements Editor upgrade.

The effective date for all products within the scope of this document for release 2016.1 is 11/05/2015 - 04/08/2016.

Enhancements

New Element for Doc Viewer text display only
Summary: A new element ‘DocViewerOnly’ can be authored in a REQ file and when set to true, the corresponding text is displayed/visable in Doc Viewer only and suppressed from the rendered PDF. The new element can be authored as a child of a Condition/Otherwise element with a child para element to define the text. The use case for this new element derived from the new rounding method implemented for the TILA-RESPA Integrated Disclosures to provide the capability to explain rounding rule details.
Technical Notes: Modified the Instance.xsd to add new element and modified RulesToErl.xsl stylesheet to strip out the element information so it does not render on the PDF.
Implementation Notes: This requires a Requirements Editor upgrade.
REQ File Name Added to PTR Editor Window
  • Type: Enhancement
  • Reference: 338046
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: Requirements Editor 3 User Guide
Summary: The “PTR Editor” window now displays the name of the document. In the upper left-hand corner of the window the document name appears after “PTR Editor”. When working with multiple REQs and PTR windows this will help differentiate the PTR Editor windows.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
Outline Editor Displays IDs for Conditions and Iterators
  • Type: Enhancement
  • Reference: 335031
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No Documentation Impact
Summary: The Outline Editor tab has been enhanced to display the ID for Conditions and Iterators formatted as COND.ID##### or ITR.ID#####. Previously, Conditions and Iterators displayed the text ‘AutoID’.
Technical Notes: Modified Outline.cs file to include ID display.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
Content References Previous/Next Navigation Toolbar
  • Type: Enhancement
  • Reference: PBI 336794
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No documentation impact
Summary: A new Content References Navigation toolbar has been added to Requirements Editor (RE3). The toolbar has two new buttons for previous and next for navigating content reference blocks within an REQ file.
Technical Notes: By default, the new toolbar is not visible. To display the toolbar, go to View>Toolbars and select Content References Navigation. This functionality originated as a navigation requirement for the Merge Tool.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
Resizable Content Reference Window
  • Type: Enhancement
  • Reference: 336153
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No documentation impact.
Summary: The Content Reference window is now resizable. This allows for resizing the window to see longer reference names without having to use the horizontal scroll bar.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.
Create HTML outlines instead of PDF for large outlines
  • Type: Enhancement
  • Reference: 365905
  • Compliance Impacts: None
  • Documentation Impacts: None
Summary: Changes were made to the PDF Outline functionality to allow for HTML outlines instead of PDF. If a PDF outline is determine too large to produce within the PDF Outline tab, it will instead be presented as HTML.
Technical Notes: If a HTML outline is preferred for all outlines instead of PDF, the following setting in Windows Registry can be added to allow for this preference: HKEY_CURRENT_USER\Software\Wolters Kluwer\RequirementsEditor\3.0\Expere\OutputOutlineFormat with the value HTML.
Implementation Notes: This enhancement requires a Requirements Editor update.
Projects Migrated to Core Shared Libraries
  • Type: Enhancement
  • Reference: 367801
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No documentation impact
Summary: ExpereNetRuntime and BuildOutlinePDF have been migrated to the Requirements.Service shared core library. resourcesLib has been migrated to the Requirements.Commonshared core library. This helps in getting core logic into the core libraries and also allows for better documentation and testing.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Tagline Separator Line
  • Type: Enhancement
  • Reference: 346328
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: Requirements Editor User Guide
Summary: The TaglineSeparatorLine attribute has been added to the Document element, providing the ability to suppress printing the Tagline separator line.
Technical Notes:
Attribute Name TaglineSeparatorLine
Values Yes, No - Default is Yes
Logic
  • If attribute is not present -or- TaglineSeparatorLine=Yes, then continue to honor printing the tagline seperator line as it does today.
  • If TaglineSeparatorLine=No, suppress printing the tagline seperator line.
Additional Information By default, if the Tagline and MetaData elements are not authored, the default behavior is to print a tagline separator line at bottom of each page. Also, presence of Tagline and/or MetaData elements will print a tagline separator line. In either scenario, adding TaglineSeparatorLine=No element will be honored and suppress printing of the tagline separator line.
Implementation Notes: This feature requires a Content Stylesheet and a Requirements Editor Tool update.
Updated I-32 Installation
  • Type: Enhancement
  • Reference: 374745
  • Compliance Impacts: This enhancement is not a compliance issue.
  • Documentation Impacts: No documentation impact.
Summary: The Requirements Editor now uses the latest released I-32 components placed the proper locations.
Technical Notes:
  • Abyss.dll version 3.15.1028 is installed to the System folder.
  • Seareach4.dll version 4.43.1100 now utilized and marked as shared.
Implementation Notes: This feature requires a Requirements Editor Tool update.

Defects

Build/Assembly Transaction when Unused Rules Exist
  • Type: Defect
  • Reference: 367213
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously, the RE3 Build and Execute Document functions caused an error if there were unused rules.
Solution: This modification provides the ability to build and assemble a transaction without errors, even if there are unused rules in the REQ (applies to dynamic docs only). Impacts both Readonly and Writeable REQ files.
Note: This modification:
  • applies to dynamic documents only
  • impacts both ReadOnly and Writeable REQ files
Implementation Notes: This requires a Requirements Editor update.
New Total First, then Round Method
  • Type: Enhancement
  • Reference: PBI 351029
  • Compliance Impacts: A New Total First, then Round Method is being added to support a future compliance related content change (targeted for the 2016.2.2 May content release).
  • Documentation: Requirements Editor 3 User Guide, Expere Developer’s Guide
Technical Notes: The Requirements Editor 3 Tool has been enhanced to add new elements and attributes to support the new rounding method. The new element and method will allow for the ability to total the items first, and then round the sum of them. The Expere Engine Stylesheet has been modified to add logic to utilize new elements/attributes and implement new rounding method to for calculating aggregated totals that then need to be rounded.
Implementation Notes: This feature requires an Expere Engine Update and Requirements Editor 3 Tool Update. A future content release will require the use of this method.
Important: The 2016.1 Expere Engine release which includes this feature will be required to support a future planned content change.

This content change will not be backwards compatible with prior versions of the Expere Engine/Tools. You are encourage to have this Engine release installed as soon as possible so it is in place prior to receiving the content update targeted for the May content release.
Changes to Title Font Emphasis and DefinedTerm
  • Type: Defect
  • Reference: 345913
  • Compliance Impacts: This is a compliance issue.
  • Documentation Impacts: None
Issue: Previously, when Title Font emphasis or DefinedTerm tags were added anywhere in text elements (such as para elements) and the element after the emphasis contained DTAs, the PTR Editor did not display the correct DTA information when editing the element.
Solution: Now, when placing Title Font emphasis or DefinedTerm tags at the beginning or in the middle of text elements that contain DTAs, the PTR Editor window displays the correct DTA information when editing the field.
Implementation Notes: This requires a Requirements Editor upgrade.
eInitials printing incorrect line widths
  • Type: Defect
  • Reference: PBI 320447
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: Requirements Editor User Guide
Issue: When generating documents that include eInitials, the line width is printing 2.5 inch, which is the length for the eSignature field. Previously, when the Esignature type 'initials' was chosen, the line coming from the signature element still printed full width.
Solution: Now, when Esignature elements are present and the type 'initials' is chosen and the Length attribute is not authored, the signature line is the same width as the Esignature initial box by default, not standard full width. If Length attribute is authored, that attribute is honored.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Editing Element Text displays as Raw XML
  • Type: Defect
  • Reference: PBI 353368
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: No documentation impact
Issue: Resolved an issue where Raw XML was displaying when editing the contents of an element that included text and a data item (DTA).
Technical Notes: Reverted a prior change and implemented a new solution that changed the SchemaLocation attribute on the InstanceReqDiff.xsd (schema file for the merge tool) to correctly reference the Instance.xsd (RE Tool main schema file).
Implementation Notes: This feature requires a Requirements Editor Tool (RE2 & RE3) update.
"Save As" Lock Up Resolved
  • Type: Defect
  • Reference: 350176
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: When performing a Save As function, if users clicked the Cancel button on the Document Properties window during the save, any future Save As functionality was disabled. Now users are able to cancel on the Document Properties screen and then save.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
Editable REQ After Save As
  • Type: Defect
  • Reference: 237525
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously, when you performed a Save As command on a read-only REQ, you could not edit the new file. The application behaved as if it was still a read-only document.
Solution: Now, When users perform a Save As command with read-only files, the new file is editable.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Spelling Correction for Requirements Document File ‘Type’ Description
  • Type: Defect
  • Reference: 346756
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: The file ‘Type’ description for Requirements Editor files when browsing using Windows Explorer was spelled incorrectly as ‘Requiements Document’.
Solution: Corrected the spelling to be ‘Requirements Document’.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
PTR Editor Window – Able to Scroll and Copy/Paste ReadOnly REQ Files
  • Type: Defect
  • Reference: 354911
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Resolved issue where the scroll bar was disabled and unable to copy/paste text for ‘Business Logic’ and ‘PTR’ fields when the REQ (RE3) file properties were set as Read Only.
Solution: Modified fields in PTR Editor to allow scrolling and copy/paste when file is Read Only.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3 only) update.
Missing Web Service Error Message
  • Type: Defect
  • Reference: 350556
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously, an error message was displayed after a user cleared the authoring web service value within Tools > Options and attempted to open an REQ file.
Solution: A change was made to alert the user while opening an REQ file if there is a missing Web Service in the Expere Configuration options.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Preview and PDF Outline tabs result in path incorrect error
  • Type: Defect
  • Reference: 355631
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue:

An error was resolved when navigating to the Preview or PDF Outlines tab in RE3.

The Preview tab generated the following error: Preview unavailable: Could not find a part of the path ‘C:\Users\firstname.lastname\Appdata\Local\Temp\RequirementsEditor\.

The PDF Outline tab generated the following error: Cannot find …:/Users/firstname.lastname/AppData/Local/Temp/Req…
Solution: A problem occurs if the folder RequirementsEditor does not exist under users\Appdata\Local\Temp directory. A check was added to see if the directory does not exist and creates it if not found.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.
REQ Filename included in application bar
  • Type: Defect
  • Reference: 313095
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: The Requirements Editor 3 application was modified to include the REQ Filename name in the application title. When the application is minimized or when using alt-tab to navigate applications, the Filename is included so the user can easily identify the session to select. If there are multiple REQ files open in a single session, the filename of the REQ that has focus is used for the name in the application title.
Solution: A setting was modified in the isolated shell to show project name before tool name, which was not set previously.
Implementation Notes: This feature requires a Requirements Editor 3 Tool update.
PTR Editor Does Not Display Rule Info after Content References Update
  • Type: Defect
  • Reference: 364386
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: When opening an REQ file that has out of date content references, the rules in those content references are not displaying in the PTR Editor Window after the content references update. The PTR editor remains blank when selecting a rule (any DTA/COND/ITR).

This also happens on updating a content reference manually, adding a new content reference and the automatic content reference update.

Solution: RE Tool was modified to reload the entire tree whenever a content reference update takes place and to expand all sections to their previous state before the update.

The PTR Editor was not displaying the rule info after the content references update because the content references were not updating the content from the web service, but the field grid was getting updated. This resulted in rules showing up in the outline editor that were not in the field grid.

Implementation Notes: This feature requires a Requirements Editor Tool (RE 3) update.
Messaging for Duplicate Element IDs Instead of Auto Renumbering
  • Type: Defect
  • Reference: 362370
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: When opening an REQ file, and user selects ‘No’ to the message asking to ‘Update Inherited Components’, duplicate Element IDs (ie. Section, Notice, TransactionGraphic, etc.) were automatically renumbered to make it unique.

Research concluded that the renumbering of IDs occurred at time of opening the REQ file, not as a result of the ‘Update Inherited Components’ messaging. System logic is in place that automatically trapped for duplicate element IDs and renumbered to make them unique which in some cases resulted in other ID duplication which in turn were renumbered as the logic for the new ID assigned does not check if the ID is already in use.

Solution: Modified the existing logic to identify the duplicate element IDs and display a message to the user instead of automatically renumbering. The user can research the duplicity to research root cause and determine remedy actions.
Implementation Notes: This feature requires a Requirements Editor Tool (RE 3) update.
Inactive Content Omitted on PDF Outline
  • Type: Defect
  • Reference: 349246
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously with PDF outlines, if content was Inactive in the Outline view it was being displayed in the PDF outline view. This is confusing for the customer because in the PDF outline view they cannot tell where Inactive content begins and ends.
Solution: All Inactive content is omitted in the PDF Outline.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Adding Attributes to Content References
  • Type: Defect
  • Reference: 349335
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified in which a user could add attributes to content refrences when they should not have that ability. This was done by right-clicking on the root of a content reference and adding a profile attribute to the content reference.
Solution: Code was modified to remove the ability to add attributes or child elements to content references.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.
Resolved error adding valid Schema to Transaction XML
  • Type: Defect
  • Reference: 364452
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue:

Previously, adding a TXN>Borrowers element in Transaction XML resulted in the following error message: An error occurred adding the element to the prototype: The reference node is not a child of this node.
Solution: Now for Transaction XML, you can add a Borrowers element at the TXN level without receiving an error, even if it exists in the Notes>Note element.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Rendition plugin for internal Requirements Editor Installer
  • Type: Defect
  • Reference: 357497
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: For Internal installations only: Previously, the E-Form Rendition package was always intalling, even after choosing Make Unavailable in the Advanced install options.
Solution: The installer was updated to ensure the following:
  • E-Form Rendition package is installed when the install package is selected.
  • E-Form Rendition package is not installed when the Unavailable option is choosen for the E-Form Rendition package in Advanced Install options.
  • Update installationss (without uninstalling first) honor the previous install decision to exclude it or include it.
  • When installed, the E-Form Rendition menu option should be available in RE3.
  • When not installed, the Rendition menu options and customizations to the PTR editor window should not appear.
  • FOP and XEP do not have this option available.
Important: Note that the previous three CAB files have now been embedded within the .MSI file.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Title Font Emphasis Has No Effect
  • Type: Defect
  • Reference: 338459
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously, when using the Title Font emphasis on text, it had no effect. The expected font change from Serif to Sans Serif was not occurring.
Solution: Now, when a Title Font emphasis is added to text, it changes the text from Serif font a Sans Serif font.
Implementation Notes: This feature requires a Requirements Editor Tool update.
OutputFormat printing issue addressed
  • Type: Defect
  • Reference: 322811
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: The following issues were reported:
  • Mapping "USA" to the "/Txn/OrgEstablishedState" enumeration printed USA on documents when selecting the "Texas" output format; the expected value should have been United States of America.
  • Mapping "NT" to the"Txn/OrgEstablishedState" enumeration printed NW Territories on documents when selecting the "Texas" output format; the expected value should have been Northwest Territories.
Solution: The issues above have been resolved. The following now print correctly on all forms:
  • United Stateds of America
  • Northwest Territories
United States of America now prints on all forms.
Implementation Notes: This feature requires a Requirements Editor Tool and Expere Engine update.
Wrong Registry Keys for Rendition
  • Type: Defect
  • Reference: 375755
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified where the installation script was creating incorrect subkeys:
  • RenditionProductionURL
  • RenditionDevelopmentURL
Solution: The installation script was modified to create the correct subkeys under the Rendition registry key:
  • ProductionURL
  • DevelopmentURL
Implementation Notes: This feature requires a Requirements Editor Tool update.
CustomerFacingOutline Creating a Corrupt PDF
  • Type: Defect
  • Reference: 355623
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified in which the Subordination Agreement-Real Estate Lien REQ generated a corrupt PDF on the Outline tab of the Requirements Editor. The same issue appeared on the Document Requirements tab of the Data Dictionary Viewer.
Solution: The PDF Outline generation issue was resolved.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update. If you generate your own PDF Outlines, this feature also requires an update to the Customer Facing Outline Application installed with the Expere Server Tools.
False Message if Runtime Request Fails
  • Type: Defect
  • Reference: 360339
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified in which the user was receiving an error when the Expere Run Time request fails and Preview tries to produce a PDF. The error that the Root Element is missing is not clear.
Solution: The following message was added if the Expere Run Time request fails when generating a preview in the preview tab in the requirements editor. No response from Expere run time performing service request.
Implementation Notes: This feature requires a Requirements Editor Tool (RE3) update.
Non-incrementing Entity IDs Resolved
  • Type: Defect
  • Reference: 367228
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: An issue was identified in which invoking the Duplicate command or copying and pasting content was not incrementing any of the entity IDs of the duplicated or pasted content.
Solution: Code was modified to ensure that IDs for entities (sections, signature sections, notices, etc.) are being correctly incremented during the Duplicate and Copy/Paste functions.
Implementation Notes: This feature requires a Requirements Editor Tool update.
Requirements Editor Installation Creating Incorrect Rendition Registry Keys
  • Type: Defect
  • Reference: 374696
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation Impacts: No documentation impact.
Issue: Previously the Requirements Editor installation was creating incorrect Rendition registry keys of :
  • RenditionProductionURL
  • RenditionDevelopmentURL
Solution: The instlalation script was updated to ensure that the following correct registry keys are being created:
  • ProductionURL
  • DevelopmentURL
Implementation Notes: This requires a Requirements Editor upgrade.